Skip to main content

Proposals

Proposal Documents​

What is a proposal document?​

Can also be called a Design Document. A Proposal Document is given to the rest of the team to gain consensus on technology changes or implementations of new systems.

Examples of where you would use a Proposal Document are:

  1. The technology and architecture being used complete a Squad's outcomes - this should be at a high level but focus on the technology changes rather than solely the business or customer outcome.
  2. A change to technology currently adopted, or a technology that is able to achieve the same outcome. Technology change may be required to achieve the goal of a Squad.
  3. The adoption of a new service, tooling or solution to allow people to comment and demonstrate the reasoning

Ideally, this forms a key part of a design change to ensure that people have the ability to be informed and give feedbacks and collaborate on making decisions.

Key Benefits​

  1. The ability for the wider team to collaborate around a proposed change to their working practices - we want to allow people to use their experiences to progress the technology department at Rapha as a collective.
  2. We can validate our choices for making decisions - and make clear the advantages and disadvantages of creating a new architecture or utilising a new technology.
  3. By being open and documenting our decisions, we're able to work towards the same goals and not have overlaps of technology or evaluate something we have already adopted.
  4. It solidifies a part of our Technology Roadmap and our Technology Radar. [1]

How to write a proposal document?​

Either using a collaborative tool like

Proposal documents should ideally be committed to our documentation side once they are past draft mode for the wider team to browse without requiring access.

  1. The Rapha Technology Radar